Label is not optional#44776
Conversation
The `label` property of `actions/upload-code-coverage` is not optional.
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Updates documentation for setting up code coverage by clarifying the LABEL parameter description.
Changes:
- Adjusts the wording for the
LABELworkflow input to remove “optional” phrasing.
| * **`COVERAGE-FILE-PATH.xml`**: The path to your Cobertura XML report (for example, `coverage.xml` or `target/site/jacoco/cobertura.xml`). | ||
| * **`LANGUAGE`**: The primary language of the code being covered (for example, `Python`, `Java`, `JavaScript`). | ||
| * **`LABEL`**: An optional label to identify this coverage report (for example, `code-coverage/pytest`). | ||
| * **`LABEL`**: A label to identify this coverage report (for example, `code-coverage/pytest`). |
How to review these changes 👓Thank you for your contribution. To review these changes, choose one of the following options: A Hubber will need to deploy your changes internally to review. Table of review linksNote: Please update the URL for your staging server or codespace. The table shows the files in the
Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server 🤖 This comment is automatically generated. |
The
labelproperty ofactions/upload-code-coverageis not optional.Why:
In the documentation for
actions/upload-code-coverage,labelis clearly identified as required. It is therefore wrong to state that it is optional.What's being changed (if available, include any code snippets, screenshots, or gifs):
Removing the word "optional" from the documentation of the
labelproperty.Check off the following: